This week in Flutter #56: The Google I/O hype is slowing down

After the hype following Google I/O, Flutter news has slowed down this week. This means fewer links than usual in this issue.

Did I miss an article you would like to see in the newsletter? Let me know in the comment section below.

- Michele Volpato

Development 🧑‍💻

🔗 Readable Unit Tests in Dart/Flutter

Flutter tests can be difficult to read, especially if you are not a developer. They can be made more clear by using some packages. Andrew Piterow wrote this article with exactly this in mind.

🔗 How to Add a Custom Test Timeout in Flutter

Andrea Bizzotto has a tip about timeouts during testing. I did not know it, did you?

🔗 Code sharing monorepos in Flutter for simple Server-Client data

An interesting approach to code sharing between two Flutter apps, a client and a server, by James. I would not follow this approach; I would keep the common code separated in a library imported by both projects. But maybe this can be a solution for small projects in one-man teams.

🔗 Micro Apps in Flutter, does it make sense?

Daniel Herrera Sanchez and his team at Bancolombia are working on multiple apps that share several functionalities. They asked themselves whether they could build micro apps containing complete experiences, instead of just reusable components.

Others 🤷‍♂️

🔗 Flutter builds are way faster with M1 machines: A comparison of VMs

I enjoyed this article by Nils Reichardt. It shows with numbers, on a real-world Flutter project, that the M1 Macs are way faster than the Intel Macs. A build time reduced by about 65% is not a joke. So you might want to switch to an M1 Mac, but then you do not have time for that coffee break while your app is building.

🔗 shared_preferences (Package of the Week) 🎦

Use shared preferences to persist storage in your app.

That’s it for this week.

If you want to comment on any of this week’s entries, you can do it in the comment section below.

Have a bug-free week,

- Michele Volpato